Summary

Issue:

For Jamloop, they have a cluster with an existing VPC and only public subnets. With the current flow, when we enable Karpenter it asks for private subnet but we dont need them (see last screenshot as we deploy in public subnet anyway)

Screenshots / Recordings

Before (when enabling Karpenter on existing VPC):

After (it doesn't ask for private subnet):

The logic is already done in the network settings (private node toggle to know if we deploy on private/public):

Testing

• Changes tested locally in the relevant Console's pages and Storybooks
• yarn test or yarn test -u (if you need to regenerate snapshots)
• yarn format
• yarn lint

PR Checklist

• I followed naming, styling, and TypeScript rules (see .cursor/rules)
• I performed a self-review (diff inspected, dead code removed)
• I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
• I only kept necessary comments, written in English (watch for useless AI comments)
• I involved a designer to validate UI changes if I am not a designer
• I covered new business logic with tests (unit)
• I confirmed CI is green (Codecov red can be accepted)
• I reviewed and executed locally any AI-assisted code